-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(cairo_native): use current dir in cairo compile #2815
Conversation
a824d83
to
3be2b64
Compare
3be2b64
to
b34c5ab
Compare
b34c5ab
to
c487834
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewed 1 of 1 files at r1, all commit messages.
Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @avi-starkware and @noaov1)
crates/blockifier/build.rs
line 9 at r1 (raw file):
let cairo_native_dir = current_dir().expect("Failed to get current directory").join(PathBuf::from("cairo_native"));
this is resolved at runtime, and the resulting dir depends on the calling context; this is desired behavior?
Code quote:
current_dir().expect("Failed to get current directory")
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @avi-starkware)
crates/blockifier/build.rs
line 9 at r1 (raw file):
Previously, dorimedini-starkware wrote…
this is resolved at runtime, and the resulting dir depends on the calling context; this is desired behavior?
@avi-starkware ?
I just reverted the changes in #2289.
Do you have other ideas?
Previously, noaov1 (Noa Oved) wrote…
Why do you want to do this? The problem with using
and running
would give you different results. Which is weird and unexpected behavior that could easily cause bugs in the future. Why are you doing this PR? |
No description provided.